Jobs
Preinstall job (introduced in v6.1.0)
The pre-install job prepares the database by seeding data, and the user provides customizations such as keys, UUID, etc. Unlike other images, it is based on debian-slim 12.
Cacheloader Vs Loader: Invoker Job Changes from v6.0.0 to v6.1.0
Cacheloader Invoker job (in v6.0.0)
This section is only applicable for Boomi Cloud API Management – Local Edition (LE) v6.0.0.
The Cacheloader invoker job has the following types of jobs:
-
On Startup job - It invokes the Cacheloader with full load options.
-
K8s cron job - It handles delta and full load as per the schedule and periodicity.
Loader Invoker job (in v6.1.0+)
This section is applicable for Boomi Cloud API Management – Local Edition (LE) v6.1.0+.
The loader job invokes services on the loader using HTTP. In tethered mode, the loader syncs with Boomi Cloud API Management and subsequently updates the entries in the cache. In untethered mode, it only updates the cache.
The loader invoker job has the following types of Kubernetes jobs and cronjobs:
loader-job-full: This job runs daily and loads all the data from the database.loader-job-delta: This job loads delta updates from the database every 15 minutes. The user can adjust this interval.- Post-install data load: This job warms up the cache, after which the cluster is ready. It is invoked via the
Helm post-installhook and deleted immediately after a successful load. - Post-upgrade data load: This job is invoked immediately after an upgrade via the
Helm post-upgradehook and is deleted immediately after a successful load. It warms up the cache on an upgrade.
You can adjust the cron schedule from Values.yaml.
- For LE v6.2.0, refer to 6.2.0 Values.yaml.
- For LE v6.1.0, refer to 6.1.0 Values.yaml.
- For LE v6.0.0, refer to 6.0.0 Values.yaml.
| In v6.0.0 | In v6.1.0 |
|---|---|
 |  |
Logsync job (introduced in v6.2.0)
The logsync job invokes services on the logcollector via HTTP. In tethered mode, it interacts with Boomi Cloud API Management (Control Center) and monitors logs at /mnt/data/access/access.log. The logsync cronjob is a scheduled Kubernetes job that periodically triggers the logcollector logsync component to process and synchronize access log data. It functions as a reliable scheduler, ensuring continuous log processing and data synchronization.
The logsync invoker job has a logsync-job type of Kubernetes job and cronjob. It reads the persistence volume and uploads data to Boomi Cloud API Management (Control Center) every 15 minutes.
Required Resources
Before installing Local Edition, refer to Prerequisites and Preinstallation Checklist.
